home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The Atari Compendium
/
The Atari Compendium (Toad Computers) (1994).iso
/
files
/
umich
/
telecomm
/
stadel
/
stadel2.zoo
/
c33c
/
c33c.doc
< prev
next >
Wrap
Text File
|
1989-02-10
|
2KB
|
46 lines
c33c STadel conversion programs c33c
SYNOPSIS
C33A_NS - convert .ml, .rfl, .sfl files to STadel 3.3x format.
C33A_SYS - convert .sys files to STadel 3.3x format.
C31TO33C - convert .sys files from STadel 3.1 to 3.3c format.
FIX33C - Channge userlog entries from 3.3a format to 3.3c format.
DESCRIPTION
These three programs convert your STadel 3.3 (3.1) files for
use with STadel 3.3c. Run these programs before* you run the
3.3c version of configure, and be sure to back up your system
before doing the conversion.
To run C33A_NS, cd to your network directory and run C33A_NS.
It will convert your 3.3 *.ml files to 3.3a format, then copy
the sendfile orders and file requests in your *.sfl & *.rfl
files into the 3.3a *.nfs files. (If you don't understand this,
don't worry about it.) As C33A_NS runs, it will display what
it's converting on the screen (2 numbers on a line are a mail
message, other messages are self-explanatory.)
To run C33A_SYS, cd to the directory that contains your
ctdltabl.sys and run C33A_SYS. It will quietly convert all the
files that need to be changed. Any output means that something
went wrong.
Running C31TO33C is a little more difficult. First you
must move your 3.1 CTDLNET.SYS and CTDLLOG.SYS files into the
same directory, cd to that directory, then run C31TO33C, passing
one argument to it - your cryptseed from your ctdlcnfg.sys. (the
#define cryptseed argument -- if you've got a cryptseed of 69,
you would run C31TO33C as `c31to33c 69'.) After running, move
the two .SYS files back to their appropriate directories.
Finally, if you are converting to 3.3c from 3.3a or 3.3b,
you don't need to run any of the above programs. Instead,
all you need to do is run FIX33C to chuffle data around in your
CTDLLOG.SYS file. This one is simple; move FIX33C into the
directory that contains your CTDLLOG.SYS file, then run it,
passing one argument - the cryptseed from your ctdlcnfg.sys
- to it. When it's done, your CTDLLOG.SYS file will be updated.